Reduced-size user interfaces for battery management

ABSTRACT

A device with a touch-sensitive display and a battery can determine a battery level of the battery, and in accordance with a determination that the battery level is at or below a first threshold value, cause a haptic output and/or enter a low-power mode. While in low-power mode, the device may produce different outputs in response to user inputs than while in a normal power mode. In some embodiments, while in the low-power mode, the device may display only the time and an indication that the device is in a low-power mode.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser.No. 62/129,882, “Reduced-size User Interfaces for Battery Management,”filed Mar. 8, 2015, U.S. Provisional Application Ser. No. 62/047,606,“Reduced-size User Interfaces for Battery Management,” filed Sep. 8,2014, and U.S. Provisional Application Ser. No. 62/034,103,“Reduced-size User Interfaces for Battery Management,” filed Aug. 6,2014, the contents of which are hereby incorporated by reference intheir entirety.

This application also relates to U.S. Provisional Patent ApplicationSer. No. 62/033,819, titled “Low Power Mode,” filed Aug. 6, 2014; U.S.Provisional Patent Application Ser. No. 62/044,894, titled “Reduced-SizeInterfaces for Managing Alerts,” filed Sep. 2, 2014; and U.S.Provisional Patent Application Ser. No. 62/026,532, titled “RaiseGesture Detection in a Device,” filed Jul. 18, 2014, the contents ofwhich are hereby incorporated by reference in their entirety.

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for managing battery use.

BACKGROUND

Reduced-size personal electronic devices, such as devices that aresmaller than cellular phones, may be used as timekeeping devices as wellas providing other applications or functions. In cases where thepersonal electronic device may be the primary timepiece of the user, itmay be important to provide timekeeping functionality for a relativelylong period of time between charging the battery of the device. Thedevice's timekeeping functionality may supersede the importance of theother applications or functions of the device.

BRIEF SUMMARY

User interfaces that can alert the user to low battery levels andprovide user interfaces and methods for extending the device's abilityto time-keep are desirable, particularly for battery-powered portableelectronic devices where battery conservation is especially beneficial.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display, a battery, and ahaptic mechanism. The method includes determining a battery level of thebattery. The method includes, in accordance with a determination thatthe battery level is at or below a first threshold value, causing thehaptic mechanism to issue a haptic output. The method includes receivingdata indicative of a user input. The method includes determining whetherthe data has been received within a predetermined time interval afterthe haptic output. The method includes, in accordance with adetermination that the data has been received within the predeterminedtime interval, displaying a battery alert on the touch-sensitivedisplay.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display, a battery, at leastone hardware button, and a rotatable input mechanism. The electronicdevice is configured to, while in a normal power mode, produce a firstoutput responsive to input at the touch-sensitive display, a secondoutput responsive to input at the at least one hardware button, and athird output responsive to input at the rotatable input mechanism. Themethod includes determining a battery level of the battery. The methodincludes, in accordance with a determination that the battery level isat or below a first threshold value: entering a low-power mode, thelow-power mode characterized in that a fourth output is producedresponsive to input at any of the touch-sensitive display, the at leastone hardware button, or the rotatable input mechanism.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display, a battery, and atleast two input mechanisms. The method includes receiving first dataindicative of an activation of a first input mechanism. The methodincludes receiving second data indicative of an activation of a secondinput mechanism, wherein the second data is received within apredetermined elapsed time period from receiving the first data. Themethod includes, in response to receiving the first data and the seconddata: determining an amount of time remaining before a level of thebattery reaches a first threshold value, displaying the amount of timeremaining, displaying an affordance for invoking a low-power mode,detecting a selection of the affordance, and in response to detectingthe selection, entering the low-power mode.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display, a haptic mechanism,and a battery, cause the electronic device to determine a battery levelof the battery; in accordance with a determination that the batterylevel is at or below a first threshold value, cause the haptic mechanismto issue a haptic output; receive data indicative of a user input;determine whether the data has been received within a predetermined timeinterval after the haptic output; and in accordance with a determinationthat the data has been received within the predetermined time interval,display a battery alert on the touch-sensitive display.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display, a battery, at leastone hardware button, and a rotatable input mechanism, cause theelectronic device to, while in a normal power mode, produce a firstoutput responsive to input at the touch-sensitive display, a secondoutput responsive to input at the at least one hardware button, and athird output responsive to input at the rotatable input mechanism;determine a battery level of the battery; and in accordance with adetermination that the battery level is at or below a first thresholdvalue, enter a low-power mode, the low-power mode characterized in thata fourth output is produced responsive to input at any of thetouch-sensitive display, the at least one hardware button, or therotatable input mechanism.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs comprising instructions isdisclosed. The instructions, when executed by one or more processors ofan electronic device with a touch-sensitive display, a battery, and atleast two input mechanisms, cause the electronic device to receive firstdata indicative of an activation of a first input mechanism; receivesecond data indicative of an activation of a second input mechanism,wherein the second data is received within a predetermined elapsed timeperiod from receiving the first data; and in response to receiving thefirst data and the second data: determine an amount of time remainingbefore a level of the battery reaches a first threshold value, displaythe amount of time remaining, display an affordance for invoking alow-power mode, detect a selection of the affordance, and in response todetecting the selection, enter the low-power mode.

In accordance with some embodiments, an electronic device is described.The electronic device includes a battery; a haptic mechanism; atouch-sensitive display; means for determining a battery level of thebattery of the electronic device; means for causing the haptic mechanismto issue a haptic output in accordance with a determination that thebattery level is at or below a first threshold value; means forreceiving data indicative of a user input; means for determining whetherthe data has been received within a predetermined time interval afterthe haptic output; and means for displaying a battery alert on thetouch-sensitive display in accordance with a determination that the datahas been received within the predetermined time interval.

In accordance with some embodiments, an electronic device is described.The electronic device includes a touch-sensitive display; a battery; atleast one hardware button; a rotatable input mechanism; means forproducing a first output responsive to input at the touch-sensitivedisplay, a second output responsive to input at the at least onehardware button, and a third output responsive to input at the rotatableinput mechanism while the electronic device is in normal power mode;means for determining a battery level of the battery; and in accordancewith a determination that the battery level is at or below a firstthreshold value: means for entering a low-power mode, the low-power modecharacterized in that a fourth output is produced responsive to input atany of the touch-sensitive display, the at least one hardware button, orthe rotatable input mechanism.

In accordance with some embodiments, an electronic device is described.The electronic device includes a touch-sensitive display; a battery; atleast two input mechanisms; means for receiving first data indicative ofan activation of a first input mechanism; means for receiving seconddata indicative of an activation of a second input mechanism, whereinthe second data is received within a predetermined elapsed time periodfrom receiving the first data; and in response to receiving the firstdata and the second data: means for determining an amount of timeremaining before a level of the battery reaches a first threshold value,means for displaying the amount of time remaining, means for displayingan affordance for invoking a low-power mode, means for detecting aselection of the affordance, and in response to detecting the selection,means for entering the low-power mode.

In accordance with some embodiments, an electronic device is described.The electronic device includes a touch-sensitive display unit; a batteryunit; a haptic mechanism unit; and a processing unit coupled to thetouch-sensitive display unit, the battery unit, and the haptic mechanismunit. The processing unit is configured to determine a battery level ofthe battery unit; in accordance with a determination that the batterylevel is at or below a first threshold value, cause the haptic mechanismunit to issue a haptic output; receive data indicative of a user input;determine whether the data has been received within a predetermined timeinterval after the haptic output; and in accordance with a determinationthat the data has been received within the predetermined time interval,enable display of a battery alert on the touch-sensitive display unit.

In accordance with some embodiments, an electronic device is described.The electronic device includes a touch-sensitive display unit; a batteryunit; at least one hardware button unit; a rotatable input mechanismunit; and a processing unit coupled to the touch-sensitive display unit,the battery unit, the at least one hardware button unit, and therotatable input mechanism unit. The processing unit is configured to,while in a normal power mode, produce a first output responsive to inputat the touch-sensitive display unit, a second output responsive to inputat the at least one hardware button unit, and a third output responsiveto input at the rotatable input mechanism unit; determine a batterylevel of the battery unit; and, in accordance with a determination thatthe battery level is at or below a first threshold value: enter alow-power mode, the low-power mode characterized in that a fourth outputis produced responsive to input at any of the touch-sensitive displayunit, the at least one hardware button unit, or the rotatable inputmechanism unit.

In accordance with some embodiments, an electronic device is described.The electronic device includes a touch-sensitive display unit; a batteryunit; at least two input mechanism units; and a processing unit coupledto the touch-sensitive display unit, the battery unit, and the at leasttwo input mechanism units. The processing unit is configured to: receivefirst data indicative of an activation of a first input mechanism unit;receive second data indicative of an activation of a second inputmechanism unit, wherein the second data is received within apredetermined elapsed time period from receiving the first data; and inresponse to receiving the first data and the second data: determine anamount of time remaining before a level of the battery unit reaches afirst threshold value, enable display of the amount of time remaining,enable display of an affordance for invoking a low-power mode, detect aselection of the affordance, and in response to detecting the selection,enter the low-power mode.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 6 illustrates exemplary user interfaces for managing batterylevels.

FIG. 7A illustrates exemplary user interfaces for managing batterylevels.

FIG. 7B illustrates exemplary user interfaces for managing batterylevels.

FIG. 7C illustrates exemplary user interfaces for managing batterylevels.

FIG. 8 illustrates exemplary user interfaces for managing batterylevels.

FIG. 9 illustrates exemplary user interfaces for managing batterylevels.

FIG. 10A illustrates exemplary user interfaces for managing batterylevels.

FIG. 10B illustrates exemplary user interfaces for managing batterylevels.

FIG. 11A illustrates exemplary user interfaces for managing batterylevels.

FIG. 11B illustrates exemplary user interfaces for managing batterylevels.

FIG. 12A illustrates exemplary user interfaces for managing batterylevels.

FIG. 12B illustrates exemplary user interfaces for managing batterylevels.

FIG. 13 is a flow diagram illustrating an exemplary process fordisplaying a user interface for managing battery levels.

FIG. 14 is a flow diagram illustrating an exemplary process fordisplaying a user interface for managing battery levels.

FIG. 15 is a flow diagram illustrating an exemplary process fordisplaying a user interface for managing battery levels.

FIG. 16 is a functional block diagram of an electronic device configuredto display a user interface in accordance with some embodiments.

FIG. 17 is a functional block diagram of an electronic device configuredto display a user interface in accordance with some embodiments.

FIG. 18 is a functional block diagram of an electronic device configuredto display a user interface in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for methods and user interfaces that alert a user to lowbattery levels on a reduced-size personal electronic device and enablemanagement of battery life. Such methods and interfaces can conservepower and increase the time between battery charges, and can also reducethe cognitive burden on a user and produce a more efficienthuman-machine interface.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, 5A-5B, and 16-18 provide a descriptionof exemplary devices for performing the techniques for managing batterylevels. FIGS. 6-12 illustrate exemplary user interfaces for managingbattery levels. The user interfaces in the figures are also used toillustrate the processes described below, including the processes inFIGS. 13-15.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, California. Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch screen displays and/or touchpads),are, optionally, used.

It should also be understood that, in some embodiments, the device isnot a portable communications device, but is a desktop computer with atouch-sensitive surface (e.g., a touch screen display and/or atouchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. Nos.: 6,323,846 (Westerman et al.), 6,570,557(Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. PatentPublication 2002/0015024A1, each of which is hereby incorporated byreference in its entirety. However, touch screen 112 displays visualoutput from device 100, whereas touch-sensitive touchpads do not providevisual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar.3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. Nos. 11/241,839, “Proximity Detector InHandheld Device”; 11/240,788, “Proximity Detector In Handheld Device”;11/620,702, “Using Ambient Light Sensor To Augment Proximity SensorOutput”; 11/586,862, “Automated Response To And Sensing Of User ActivityIn Portable Devices”; and 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or

GLONASS or other global navigation system) receiver (not shown) forobtaining information concerning the location and orientation (e.g.,portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including ,withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSer. No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSer. No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensor, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514. Personalelectronic device 500 can also include haptic mechanism 542. Hapticmechanism 542 may issue a vibration or other haptic output that can beperceived by a user. In some embodiments, haptic mechanism 542 may issuehaptic outputs in a manner similar to that described for tactile outputgenerator 167 of device 100.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 1300-1500 (FIGS. 13-15).The computer-executable instructions can also be stored and/ortransported within any non-transitory computer-readable storage mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Battery User Interfaces

The battery user interfaces described below are illustrated by exemplarysequences of screens that device 500 can display in response todetermining various battery levels and detecting various user inputs. Inthese sequences, the arrows indicate the order in which the screens aredisplayed.

Displaying Battery Alerts

In some embodiments, a personal electronic device, such as device 500,can have one or more batteries that are collectively referred to as abattery. Device 500 can determine whether its battery level is at orbelow a threshold value. In some embodiments, device 500 may monitor thebattery level continuously or intermittently to determine whether thebattery level is at or below a threshold value. In some embodiments,device 500 may receive data indicating that the battery level is at orbelow the threshold value.

FIG. 6 depicts an exemplary screen 610 that device 500 can display ontouchscreen 504 in response to a determination that the battery level isat or below a threshold value. As shown in FIG. 6, initially,touchscreen 504 may be inactive. In some embodiments, when touchscreen504 is inactive, it may be unresponsive to touch inputs, or may not beactively displaying content. In some embodiments, when touchscreen 504is inactive, it is turned off. Device 500 may determine that the batterylevel is at or below the threshold value while touchscreen 504 isinactive. In accordance with a determination that the battery level isat or below the threshold value, device 500 can alert the user that thebattery level is low by causing a haptic mechanism to issue a hapticoutput 606, such as a vibration, on device 500 that can be perceived bythe user. In some embodiments, instead of causing a haptic output,device 500 can cause an audible or visible output to alert the user thatthe battery level is low.

In some embodiments, the threshold value may be a percentage of a totalbattery level. In some embodiments, the total battery level may be themaximum battery capacity; that is, the battery level at which thebattery is fully charged. In this scenario, when the battery reaches athreshold value of 0% of the total battery level, the battery is fullydischarged.

In some embodiments, the total battery level may be the maximum batterylevel of the battery minus a reserve amount of battery capacity, wherethe reserve amount is reserved for performing essential operations suchas displaying the current time. In this scenario, when the batteryreaches 0% of the total battery level, the battery may still contain thereserve amount of capacity.

The total battery level may be a constant value, or may vary over timedue to temperature or degradation. In some embodiments, determiningwhether the battery level is at or below a threshold value includesdetermining whether the battery level has fallen to or below thethreshold value, as opposed to determining whether the battery level hasrisen to the threshold value while being charged.

Returning to FIG. 6, after device 500 has determined that the batterylevel is at or below the threshold value and caused haptic output 606,the user may respond to the haptic output by providing an input todevice 500. In response to receiving data indicative of an input fromthe user within a predetermined time interval after the haptic output,device 500 can display screen 610 with battery alert 612. (The dashedline shown in FIG. 6 is intended to indicate the contents of the batteryalert, but may not be displayed on touchscreen 504.) In someembodiments, displaying battery alert 612 involves displaying ananimation that slides battery alert 612 upwards from the bottom oftouchscreen 504.

In some embodiments, the input from the user may be a movement of device500 that can be detected by an accelerometer and/or gyroscope on device500. Such a movement may correspond to the user moving device 500 into aposition in which the user can view touchscreen 504. The movement mayinclude a rotation and/or translation of device 500. For example, ifdevice 500 is worn on a user's wrist, the movement may correspond to theuser raising their wrist for viewing touchscreen 504. Techniques fordetecting a raise gesture are described in U.S. Provisional PatentApplication Ser. No. 62/026,532, “Raise Gesture Detection in a Device,”filed Jul. 18, 2014, the content of which is hereby incorporated byreference for all purposes.

In other embodiments, the user input may be a touch on touchscreen 504,or a depression and/or rotation of one or more input mechanisms.

Battery alert 612 includes an affordance 614 indicating the batterylevel. In this example, the affordance includes the percentage of thetotal battery level. Battery alert 612 also includes a low-batterymessage 616.

As previously discussed, device 500 can display battery alert 612 inresponse to receiving data indicative of a user input within apredetermined time interval after device 500 causes the haptic output.In some embodiments, the predetermined time interval may be in the rangeof 0 seconds to 3 minutes. In other examples, the predetermined timeinterval may be in the range of 0 seconds to 1 minute. In yet otherexamples, the predetermined time interval may be set by the user, or maybe determined by device 500 based on previous user behavior such as anaverage of previous elapsed times prior to the user providing the input.

The sequence depicted in FIG. 6 may correspond to the case when theuser, having perceived the haptic output caused by device 500, wishes topromptly view battery-related information and therefore moves device 500into a position suitable for viewing touchscreen 504 within thepredetermined time interval.

If device 500 causes the haptic output and then does not detect the userinput within the predetermined time interval after the haptic output,device 500 may remain in its initial inactive state without displayingscreen 610. This scenario may correspond to the case when the user doesnot wish to promptly view battery-related information, and thereforedoes not move device 500 into position for viewing touchscreen 504 afterperceiving the haptic output.

In some embodiments, device 500 may cause a first haptic output inresponse to detecting that the battery level is at or below a firstpredetermined threshold, and then cause a second haptic output inresponse to detecting that the battery level is at or below a secondpredetermined threshold, where the second predetermined threshold islower than the first predetermined threshold. Thus, device 500 may alertthe user multiple times that the battery level is low.

In some embodiments, the first predetermined threshold is 10% of thetotal battery level, and the second predetermined threshold is 5% of thetotal battery level. In some embodiments, device 500 may cause hapticoutputs at other predetermined thresholds.

In some embodiments, the battery alert displayed in response todetecting the user input may depend on the predetermined threshold. Forexample, the exemplary battery alert depicted in FIG. 6, correspondingto the case when the threshold is 10% of the total battery level,includes the indication of the threshold value 614 and a low-batterymessage 612. In contrast, as shown in FIG. 7A, the exemplary batteryalert displayed for the case when the threshold is 5% of the totalbattery level may include a message 710 that device 500 willautomatically enter a low-power mode if device 500 subsequentlydetermines that the battery level is at or below a minimum batterylevel, such as approximately 0% of the total battery level.

As shown in FIG. 7B, in response to a determination that the batterylevel is at or below the minimum battery level, device 500 canautomatically enter a low-power mode and display screen 704. Screen 704includes the current time 706 and may include an indication 708 thatdevice 500 is in low-power mode. The low-power mode is described in moredetail with respect to FIGS. 10A-B.

In some embodiments, as depicted in FIG. 7C, in response to adetermination that the battery level is at or below the minimum batterylevel, device 500 can display screen 712. Screen 712 includesconformation affordance 716 for confirming that the user wishes to placedevice 500 in the low-power mode. In response to detecting a selectionof confirmation affordance 716, device 500 can enter the low-power modeand display screen 704.

Dismissing Battery Alerts

In some embodiments, while screen 610 is displayed (as shown in FIG. 6),if device 500 receives data indicative of a second user input, device500 can dismiss battery alert 612. Dismissing battery alert 612 mayinclude removing battery alert from touchscreen 504. In someembodiments, dismissing battery alert 612 may include displaying ananimation that slides battery alert 612 off the bottom of touchscreen504.

In some embodiments, the second user input may correspond to a movementof device 500. Returning to the example of device 500 being worn on awrist, the second user input may correspond to a user moving device 500out of a viewing position by, for example, rotating device 500 out ofposition for viewing or lowering their wrist. These scenarios maycorrespond to the case when the user, having viewed the battery alert,does not wish to continue viewing or interacting with device 500 andtherefore moves device 500 out of the viewing position. Device 100 maythen return to an inactive state to conserve power.

In some embodiments, a user may also dismiss a battery alert by makingcontact with touchscreen 504. As shown in FIG. 8, if while displayingscreen 610 device 500 detects a contact on touchscreen 504, then device500 can slide battery alert 612 downwards on touchscreen 504 and displaydismissal indicator 802. The contact may comprise a touch detected ontouchscreen 504 at a first location followed by a movement of the touchfrom the first location to a second location on touchscreen 504 withoutbreaking contact of the detected touch, followed by a release (e.g., alift-off) of the touch. The movement may be a substantially downwardswipe or flick on touchscreen 504, for example. In some embodiments, ifthe user continues to swipe or flick downwards after the dismissalindicator is displayed, device 500 can dismiss the battery alert.

In some embodiments, device 500 may require the user to swipe or flickmost or all of the way down touchscreen 504 to dismiss battery alert612. For example, device 500 can determine whether the movement of thetouch exceeds a threshold distance. If the movement exceeds thethreshold distance, then in response to detecting the release of thetouch, device 500 can dismiss the battery alert. If the movement doesnot exceed the threshold distance, then in response to detecting therelease of the touch, device 500 can slide the battery alert back to itsoriginal position on touchscreen 504 without dismissing battery alert612. While the above embodiment was described with sliding the alertdownwards in response to a downward swipe or flick, one of ordinaryskill will appreciate that any other direction is also contemplated forboth the direction of the sliding and the swipe directionality.

In some embodiments, device 500 can respond to detection of differentdismissal inputs (such as data indicative of a user moving device 500out of a viewing position versus a downward swipe on touchscreen 504)differently. For example, if device 500 detects data indicative of auser moving device 500 out of position for viewing, device 500 mayassume that the user is no longer viewing touchscreen 504, and thereforemay inactivate touchscreen 504 after dismissing the battery alert. Incontrast, if device 500 detects a touch on touchscreen 504 followed by amovement of the touch (such as a downward swipe or flick), device 500may assume that the user is still actively viewing touchscreen 504, andas shown in FIG. 8 device 500 may instead display a home screen 804 oranother screen after dismissing the battery alert.

Displaying Additional Battery Information

Turning now to FIG. 9, as previously discussed with respect to FIG. 6,device 500 can display battery alert 612 in response to detecting a userinput within a predetermined time interval following the haptic outputcaused by device 500. If, after displaying battery alert 612 device 500does not detect a second user input within a second predetermined timeinterval, then device 500 can display screen 906 on touchscreen 504. Thesecond user input may be data indicative of the user moving device 500out of the viewing position by lowering it or rotating it, for example.Thus, if the user does not move device 500 after battery alert 612 isdisplayed, device 500 can display screen 906. This scenario maycorrespond to the case when the user, having viewed battery alert 612,wishes to view additional battery-related information and therefore doesnot dismiss battery alert 612. Instead, the user maintains device 500 inthe viewing position and waits for additional battery-relatedinformation to be displayed on touchscreen 504 after the secondpredetermined time interval has elapsed. The second predetermined timeinterval may be in the range of 3-10 seconds, for example.

Screen 906 includes an indication of the threshold value 902, and mayinclude an indication of an estimated amount of time 904 remainingbefore device 500 enters a low-power mode (such as described withrespect to FIGS. 7A-C). In some embodiments, device 500 can determinethe estimated amount of time remaining based on the current batterylevel and the average power consumption of device 500, on the dischargerate of the battery, or on other factors, for example.

Device 500 can also display screen 906 in response to detecting acontact with touchscreen 504 while battery alert 612 is displayed. Inthis scenario, the user may not wish to wait for the secondpredetermined time interval to elapse before viewing the additionalbattery-related information, and instead makes contact with touchscreen504 to invoke immediate display of additional battery information. Inresponse to detecting the contact with touchscreen 504, device 500 candisplay screen 906.

In some embodiments, the contact for invoking display of screen 906 isan upward swipe on touchscreen 504 while screen 610 is displayed. Inother examples, the contact is a touch (e.g., a finger tap) at alocation on touchscreen 504 that corresponds to battery alert 612. Whilethe above embodiment was described in response to an upward swipe orflick, one of ordinary skill will appreciate that any other direction isalso contemplated for the swipe directionality.

Low-Power Mode

As previously discussed with respect to FIGS. 7A-B, device 500 mayautomatically enter a low-power mode after detecting that the batterylevel is at or below a threshold value, or may enter a low-power mode inresponse to detecting a selection of an affordance (as in, for example,FIG. 7C, 11, and 12). A low-power mode may be a mode in which device 500operates to reduce power consumption and extend battery life. In someembodiments, while in low-power mode device 500 can display only a timeof day and may include an indication that device 500 is in the low-powermode. Thus, in such embodiments, the ability to display the current timeis preserved but other functionalities of device 500 may be disabled inorder to provide a maximum duration of displaying the time.

In some embodiments, while operating in low-power mode, device 500 mayrespond to user inputs differently than when device 500 is operating ina normal power mode. For example, when device 500 is operating in anormal power mode, device 500 may respond to inputs normally, such as bydisplaying application icons, launching applications, performing variousfunctions, etc. Such inputs may include inputs from one or more of inputmechanisms (e.g., buttons) 506, 508, contacts on the touchscreen 504, ordata received from accelerometers or gyroscopes, for example. Incontrast, while operating in the low-power mode, device 500 may respondto these (same) inputs by displaying a single, particular output. Insome embodiments, in response to user input while in low-power mode,device 500 may power on its display to only display the current timeand/or an indication that it is operating in a low-power mode. In someembodiments device 500 may respond to user inputs differently dependingon whether the battery level has dropped below a first battery thresholdor a second battery threshold.

FIG. 10A depicts an example of device 500 detecting a particular input(such as a depression) on input mechanism 506 while operating in anormal power mode, and responding to this particular input by displayinghome screen 1002. FIG. 10B depicts an example of device 500 detectingthe same particular input on input mechanism 506 while operating in alow-power mode, and responding to the particular input by displaying thecurrent time and, optionally, an indication that device 500 is inlow-power mode, rather than by displaying home screen 1002.

In some embodiments, device 500 may display the time in a first colorbefore determining that the battery level is at or below a thresholdvalue, and display the time in a second color different from the firstcolor after determining that the battery level is at or below thethreshold value. This technique may provide the user with a visualindication of whether device 500 is operating in a low-power mode, andmay reduce the power consumption of device 500 if the power needed todisplay the time in the second color is lower than the power needed todisplay the time in the first color.

In some embodiments, device 500 may reduce the number of pixels used todisplay the time once device 500 enters the low-power mode. Thisreduction in pixels may reduce the power required to display the currenttime.

In some embodiments, device 500 may combine the above-describedtechniques for reducing the power needed to display the time while in alow-power mode; that is, device 500 may use different colors to displaythe time before and after determining that the battery level is at orbelow a threshold value and also use fewer pixels to display the timeonce device 500 enters the low-power mode.

In some embodiments, while device 500 is in a low-power mode, device 500can vary the location of the time displayed on the display to preventburn-in of the display while using the location of the displayed time toprovide the user with quick visual cues regarding the current time ofday. Notably, in such embodiments, the change in location of thedisplayed time provides more than a simple screen-saving mechanism that(for example) randomly changing display locations to prevent burn-in by“bouncing” the displayed text or affordances around the display. In sucha simple screen-saving mechanism, the changing location of the displayedtime is unrelated to the current time of day, and may frustrate or annoythe user by displaying the time in relatively unpredictable ornon-intuitive locations on the display. In contrast, in someembodiments, device 500 may translate or animate the displayed time suchthat the time is displayed at locations ranging from the “top” of thedisplay to the “bottom” of the display in proportion to the time of day.For example, a time of 00:01 (one minute after midnight on a 24-hourclock) may be displayed near the top of the display, and a time of 23:59may be displayed near the bottom of the display. In this case, becausethe display location of the time is related to the time of day, the usercan quickly estimate or discern the approximate time of day by glancingat the vertical placement of the displayed time. Similarly, device 500may display the time at locations ranging from the “left” of the displayto the “right” of the display in proportion to the time of day, or maydisplay the time at locations ranging diagonally across the display inproportion to the time of day. A person of skill in the art willappreciate that there are many ways to determine display location basedon the time of day. This display approach enhances the man-machineinteraction because the machine can prevent burn-in of the displaywithout frustrating the user as to the location of the displayed time.

Entering and Exiting Low-Power Mode

In some embodiments, device 500 can automatically enter the low-powermode in response to detecting that the battery level is at or below athreshold value, as described with respect to FIGS. 7A-B. In someembodiments, device 500 may cause a haptic output to alert the user thatthe device is entering the low-power mode, and then automatically enterthe low-power mode.

In some embodiments, as described with respect to FIG. 7C, in responseto detecting that the battery level is at or below the threshold value,device 500 may display screen 712 with confirmation affordance 716 priorto entering the low power mode, requesting that the user confirm thatthey wish to place device 500 in the low-power mode. In response todetecting a selection of the confirmation affordance 716, device 500enters the low-power mode.

If device 500 enters the low-power mode after detecting that the batterylevel is at or below the threshold level (such as by entering thelow-power mode automatically or in response to detecting a selection ofthe confirmation affordance, as described above), device 500 maysubsequently automatically exit the low-power mode when the battery isrecharged above a threshold value. The threshold value may be 10%, 15%,20%, or 30% of a total battery level, for example.

In some embodiments, device 500 may provide a user interface that allowsa user to manually place device 500 in the low-power mode. A user maywish to place device 500 in the low-power mode in cases where the userdoes not need most of the functions of device 500 but still wishes tohave access to the timekeeping function of device 500 and/or wishes toextend the battery life of device 500, for example. For example, a userwho is traveling without a battery charger may wish to reduce power useon device 500 by placing device 500 in the low-power mode during so thatdevice 500 remains functional for a longer duration.

FIG. 11A depicts a sequence of screens that device 500 can display toallow a user to manually place device 500 in a low-power mode, inaccordance with some embodiments. In response to detecting a user input,device 500 may display screen 1102. The user input may be a touch on anicon or a swipe on touchscreen 504, for example. Screen 1102 includes anaffordance 1104 indicating a current battery level. In this example, thecurrent battery level is 60% of a total battery level. Affordance 1104may include a numeric indicator of the current battery level and/or avisual gauge of the current battery level, in this case indicated by thepercentage of the circle (approximately 60%) that is displayed asthickened.

In response to detecting a second user input, device 500 can displayscreen 1106, which includes an affordance 1108 for placing device 500into the low-power mode. In response to detecting a selection of theaffordance, device 500 can enter the low-power mode. In someembodiments, selection of affordance 1108 includes a touch or swipe ontouchscreen 504 at a location corresponding to affordance 1108. In someembodiments, when device 500 enters the low-power mode, device 500displays the time and an indication that device 500 is in the low-powermode.

FIG. 11B depicts a sequence of screens that device 500 can display toallow a user to manually place device 500 in a low-power mode, inaccordance with some embodiments. In response to detecting a user input,device 500 may display screen 1202. In some embodiments, the user inputmay be a touch on an icon on touchscreen 504. For example, the input isswipe upwards from the bottom edge of touchscreen 504, or aleft-to-right or right-to-left swipe from an edge of the touch screen.Screen 1202 includes an affordance 1204 indicating a current batterylevel. In this example, the current battery level is 60% of a totalbattery level. Screen 1202 also includes an affordance 1206 for placingdevice 500 into the low-power mode.

In some embodiments, in response to detecting a selection of affordance1206, device 500 can optionally display screen 1208. The selection ofaffordance 1206 may be a touch or swipe on touchscreen 504 at a locationcorresponding to affordance 1206, for example. Screen 1208 includes anaffordance 1214 for confirming that device 500 should enter thelow-power mode, and an affordance 1216 for foregoing placement intolow-power mode. In response to detecting a selection of affordance 1214,device 500 can enter the low-power mode. The selection of affordance1214 may be a touch or swipe on touchscreen 504 at a locationcorresponding to affordance 1214, for example. In response to detectinga selection of affordance 1216, device 500 returns to displaying screen1202. The selection of affordance 1216 is a touch or swipe ontouchscreen 504 at a location corresponding to affordance 1216, forexample. In some embodiments, device 500 enters low-power mode inresponse to selection of affordance 1206 without the display of screen1208.

FIG. 12A depicts another sequence of screens that device 500 can displayto allow a user to manually place device 500 in a low-power mode. Inresponse to detecting a user input, device 500 may display screen 1222.In some embodiments, the user input may be a depression of inputmechanism 508 or 506. Screen 1222 includes an affordance 1224 forplacing device 500 into the low-power mode. In response to detecting aselection of affordance 1224, device 500 can enter the low-power mode.In some embodiments, selection of affordance 1224 includes a touch orswipe on touchscreen 504 at a location corresponding to affordance 1224.In some embodiments, when device 500 enters the low-power mode, device500 displays the time and an indication that device 500 is in thelow-power mode.

In some embodiments, affordance 1224 for placing device 500 intolow-power mode is disabled on screen 1222 when device 500 is charging.For example, when device 500 is connected to an external power source,affordance 1224 is greyed out on screen 1222 and cannot be selected.

As another example, when device 500 is connected to a power source,affordance 1224 is replaced with a different affordance or visual objectindicating that the device is charging. In both examples, the usercannot manually place device 500 into the low-power mode from screen1222.

In some embodiments, a visual object may be displayed responsive to theelectronic device determining that the device is connected to a powersource, and optionally may be displayed, at least in part, as a symbol(e.g., lightning bolt) indicating that the battery is connected to thepower source.

In some embodiments, the visual object may indicate a charge level ofthe battery. The charge level may be represented using a numericalpercentage and/or may be represented using a ring-shaped visual objecthaving clockwise (or counterclockwise) animation. In some instances,portions of ring-shaped visual objects may be selectively displayed suchthat the amount of a ring displayed corresponds to the level at whichthe battery is charged. By way of example, a battery having 50% chargemay be displayed as a semi-circle and a battery having a 75% charge maybe displayed as a three-quarter circle.

In some embodiments, the visual object may further be displayed usingone or more colors. For example, a color by which the visual object isdisplayed may be based on a charge threshold. If the percentage at whichthe battery is charged is greater than a threshold, the visual objectmay be displayed with a first color (e.g., green) and if the percentageat which the battery is charged is equal to or less than a threshold,the visual object may be displayed with a second color (e.g., red).

Referring back to FIG. 12, in some embodiments, screen 1222 alsoincludes a power off affordance 1226 for powering off device 500, a lockaffordance 1228 for locking and/or unlocking device 500, and a cancelaffordance 1230 for canceling a selection and, optionally, returning toscreen 1004.

In some embodiments, the availability of lock affordance 1228 on screen1222 is based on one or more settings of device 500. An exemplary devicesetting that affects the display of affordance 1228 is an accessibilityfeature that improves the functioning of device 500 when worn on aprosthetic limb (or other usage scenarios where contact with the device'user's skin is insufficient or undetectable). If device 500 is set toautomatically detect whether it is being worn by a human user, lockaffordance 1228 is not displayed on screen 1222. In contrast, if device500 is set to bypass detection of whether it is being worn by a humanuser, lock affordance 1228 is displayed on screen 1222 to permit manuallocking of the device.

If lock affordance 1228 is displayed on screen 1222, device 500 allows auser to manually lock the device by selecting lock affordance 1228. Asshown in FIG. 12A, when device 500 is unlocked, screen 1222 includeslock affordance 1228 for locking device 500. In response to detecting aselection of lock affordance 1228, device 500 becomes locked. In someembodiments, selection of lock affordance 1228 includes a touch or swipeon touchscreen 504 at a location corresponding to lock affordance 1228.In some embodiments, lock affordance 1228 includes a slider switch, andselection of lock affordance 1228 includes a touch or swipe ontouchscreen 504 to toggle the switch. In some embodiments, locked device500 displays screen 1006 to indicate that the device is locked, as shownin FIG. 12B.

FIG. 12B depicts a sequence of screens that device 500 can display toallow a user to manually unlock device 500. When device 500 is locked, auser may access screen 1222 by activating button 508, for example.Screen 1222 includes affordance 1228 for unlocking device 500.Affordance 1228 optionally indicates the current locked state of device500. For example, affordance 1228 can have associated verbiage “locked.”For example, affordance 1228 can be displayed as a slider switch in itslocked position. In response to detecting a selection of affordance1228, device 500 initiates an unlock process. In some embodiments, whendevice 500 initiates the unlock process, device 500 requests entry of apasscode, as shown in screen 1212.

In some embodiments, device 500 may allow a user to place device 500 ina low-power mode without using a user interface or viewing touchscreen504. For example, device 500 may enter a low-power mode in response todetecting user inputs on one or more of the input mechanisms. Asdiscussed with respect to FIGS. 5A-B, in some embodiments, device 500includes two input mechanisms (such as buttons) 506, 508. In theseembodiments, in response to detecting that the user has depressed bothof the input mechanisms 506, 508 simultaneously or nearlysimultaneously, device 500 can enter the low-power mode. In someembodiments, device 500 can enter the low-power mode in response todetecting a depression or rotation of only one of the input mechanisms,or in response to detecting a different sequence or combination ofdepressions or rotations of the input mechanisms.

If device 500 is in the low-power mode and the battery level is above aminimum battery level, device 500 may allow a user to cause device 500to manually exit low-power mode without recharging the battery. In someembodiments, device 500 can exit low-power mode in response to detectinga depression or rotation of one or more input mechanisms 506, 508. Insome embodiments, device 500 may determine if the depression or rotationof the one or more input mechanisms exceeds a threshold time duration.If the duration exceeds the threshold, device 500 may exit the low-powermode. Otherwise, device 500 may remain in the low-power mode. Thus, insome examples, a user may cause device 500 to manually exit thelow-power mode by pressing and holding one or more buttons on device500, for example.

If the battery of device 500 is at or below a minimum battery level—suchas approximately 0% of the total battery level, for example—device 500may ignore a user input requesting to exit the low-power mode, and mayremain in low-power mode until the battery is recharged to a minimumbattery level. After the battery has been recharged to at or above theminimum battery level, device 500 may automatically exit the low-powermode, or may exit the low-power mode in response to detecting a userinput as described above.

Processes for Displaying and Managing Battery Levels

FIG. 13 is a flow diagram illustrating process 1300 for managing abattery power level. Process 1300 may be performed at an electronicdevice with a touch-sensitive display screen, such as device 100, 300and/or 500 (e.g., FIGS. 1, 3, and 5). At block 1302, the devicedetermines whether the battery level is at or below a threshold level.At block 1304, in accordance with a determination that the battery levelis at or below the threshold, device 500 causes a haptic mechanism(e.g., haptic mechanism 542) to issue a haptic output. At block 1306,the device receives data indicative of a user input. At block 1308, thedevice determines whether the data was received within a predeterminedtime interval after the haptic output. In accordance with adetermination that the data was received within the predetermined timeinterval, at block 1310, the device displays a battery alert. Thedisplayed battery alert may be drawn from the examples depicted in FIGS.6, 7A-C, 8, or 9, for example. Optionally, the battery level isdetermined while the display is inactive. Optionally, the devicedetermines whether second data has been received within a secondpredetermined time interval. In accordance with a determination that thesecond data has not been received within the second time interval, thedevice determines an estimated amount of time remaining before thebattery level reaches a second threshold. The device displays the amountof time remaining. The time remaining may be displayed as depicted inFIG. 9, for example.

Note that details of the processes described above with respect toprocess 1300 (e.g., FIGS. 13 and 6) are also applicable in an analogousmanner to the other processes described herein. For example, processes1400 and 1500 may include one or more of the characteristics of thevarious processes described above with reference to process 1300. Forbrevity, these details are not repeated in the descriptions of the otherprocesses. The various methods and techniques described above withreference to method 1300 may be optionally implemented as one or morehardware units, such as those described with regard to FIG. 16.

FIG. 14 is a flow diagram illustrating process 1400 for managing abattery power level. Process 1400 may be performed at an electronicdevice with a touch-sensitive display, such as device 100, 300 and/or500 (e.g., FIGS. 1, 3, and 5). At block 1402, the device determineswhether the battery level is at or below a threshold level. At block1404, in accordance with a determination that the battery level is at orbelow the threshold, the device enters a low-power mode. The low-powermode is characterized by the device producing the same particular outputin response to an input at any of a touch-sensitive display, button, orrotatable input mechanism, wherein the particular output is differentfrom an output produced by the device in response to the same input atany of the touch-sensitive display, button, or rotatable input mechanismwhile the device is in a normal power mode. One example of such behavioris depicted in FIGS. 10A-B.

Optionally, entering the low-power mode comprises displaying aconfirmation affordance for confirming that the user wishes to enter thelow-power mode, and, in response to detecting a selection of theconfirmation affordance, entering the low-power mode.

Optionally, the particular output produced in low-power mode includesthe current time. Optionally, the particular output produced inlow-power mode includes an indication of the battery level. Optionally,while in the low-power mode, the device also produces the particularoutput in response to receiving data from an accelerometer and/orgyroscope that exceeds a predetermined value.

Note that details of the processes described above with respect toprocess 1400 (e.g., FIGS. 14 and 7A-C) are also applicable in ananalogous manner to the other processes described herein. For example,processes 1300 and 1500 may include one or more of the characteristicsof the various processes described above with reference to process 1400.For brevity, these details are not repeated in the descriptions of theother processes. The various methods and techniques described above withreference to method 1400 may be optionally implemented as one or moreunits, such as those described with regard to FIG. 17.

FIG. 15 is a flow diagram illustrating process 1500 for managing abattery power level. Process 1500 may be performed at an electronicdevice with a touch-sensitive display, such as device 100, 300 and/or500 (e.g., FIGS. 1, 3, and 5). At block 1502, the device receives firstdata indicating activation of a first input mechanism. At block 1504,the device receives second data indicating activation of a second inputmechanism, where the second data is received within a predetermined timeperiod after receiving the first data. At block 1506, in response toreceiving the first data and second data, the device determines theamount of time remaining before the battery level reaches the thresholdand displays the amount of time remaining and an affordance. At block1508, the device detects a selection of the affordance. In response todetecting the selection, at block 1510, the device enters a low-powermode. Optionally, while in the low-power mode, the device receives dataindicating a depression of a rotatable input mechanism. The devicedetermines the duration of the depression. If the duration exceeds athreshold, the device exits the low-power mode.

Note that details of the processes described above with respect toprocess 1500 (e.g., FIG. 15) are also applicable in an analogous mannerto the other processes described herein. For example, processes 1300 and1400 may include one or more of the characteristics of the variousprocesses described above with reference to process 1500. For brevity,these details are not repeated in the descriptions of the otherprocesses. The various methods and techniques described above withreference to method 1500 may be optionally implemented as one or moreunits, such as those described with regard to FIG. 18.

In accordance with some embodiments, FIG. 16 shows an exemplaryfunctional block diagram of an electronic device 1600 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 1600 are configured to perform the techniques described above.The functional blocks of the device 1600 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 16 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 16, an electronic device 1600 includes atouch-sensitive display unit 1602, a battery unit 1606, a hapticmechanism unit 1608, and a processing unit 1610 coupled totouch-sensitive display unit 1602, battery unit 1606, and hapticmechanism unit 1608. Processing unit 1610 includes a battery leveldetermining unit 1612, a haptic mechanism controlling unit 1614, a datareceiving unit 1616, a time determining unit 1618, and a displayenabling unit 1620. Optionally, electronic device 1600 includes ahardware button unit 1650, a rotatable input mechanism unit 1652, anaccelerometer unit 1654, and a gyroscope unit 1656, all of which arecoupled to processing unit 1610. Optionally, processing unit 1610includes an input detecting unit 1622, an output producing unit 1624,and a power mode unit 1626.

Processing unit 1610 is configured to: determine (e.g., with batterylevel determining unit 1612) a battery level of battery unit 1606; inaccordance with a determination that the battery level is at or below afirst threshold value, cause haptic mechanism unit 1608 (e.g., withhaptic mechanism controlling unit 1614) to issue a haptic output;receive (e.g., with data receiving unit 1616) data indicative of a userinput; determine (e.g., with time determining unit 1618) whether thedata has been received within a predetermined time interval after thehaptic output; and in accordance with a determination that the data hasbeen received within the predetermined time interval, enable (e.g., withdisplay enabling unit 1620) a display of a battery alert ontouch-sensitive display unit 1602.

In some embodiments, processing unit 1610 is further configured todetermine (e.g., with battery level determining unit 1612) the batterylevel while touch-sensitive display unit 1602 is inactive.

In some embodiments, the data indicative of a user input is a first dataand the user input is a first user input, and processing unit 1610 isfurther configured to: after enabling the display of the battery alert,receive (e.g., with data receiving unit 1616) second data indicative ofa second user input; determine (e.g., with time determining unit 1618)whether the second data indicative of the second user input has beenreceived within a second time interval after enabling the display of thebattery alert; in accordance with a determination that the second datahas been received within the second time interval, remove (e.g., withdisplay enabling unit 1620) the display of the battery alert fromtouch-sensitive display unit 1602; and in accordance with adetermination that the second data has not been received within thesecond time interval: determine (e.g., with time determining unit 1618)an amount of time remaining before the battery level reaches a secondthreshold level, and enable (e.g., with display enabling unit 1620) adisplay of the amount of time remaining on touch-sensitive display unit1602.

In some embodiments, the second user input corresponds to a movement ofelectronic device 1600.

In some embodiments, processing unit 1610 is further configured to:while touch-sensitive display unit 1602 is displaying the battery alert,detect (e.g., with input detecting unit 1622) a third user input; and inresponse to detecting the third user input: determine (e.g., with timedetermining unit 1618) an amount of time remaining before the batterylevel reaches a second threshold level, and enable (e.g., with displayenabling unit 1620) a display of the amount of time remaining ontouch-sensitive display unit 1602.

In some embodiments, the third user input is a contact on thetouch-sensitive display unit 1602.

In some embodiments, processing unit 1610 is further configured to:detect (e.g. input detecting unit 1622) a swipe on touch-sensitivedisplay unit 1602 while touch-sensitive display unit 1602 is displayingthe battery alert; and in response to detecting the swipe, remove (e.g.display enabling 1620) the display of the battery alert fromtouch-sensitive display unit 1602.

In some embodiments, the swipe is a substantially downward swipe.

In some embodiments, processing unit 1610 is further configured to:remove the display of the battery alert by enabling (e.g., with displayenabling unit 1620) a display of an animation that slides the batteryalert off-screen in the direction of the swipe.

In some embodiments, processing unit 1610 is further configured to:remove the display of the battery alert from touch-sensitive displayunit 1602 by causing (e.g., with display enabling unit 1620) a displayof touch-sensitive display unit 1602 to become inactive.

In some embodiments, processing unit 1610 is further configured to:enable the display of the battery alert by enabling (e.g., with displayenabling unit 1620) a display of an animation that slides the batteryalert upwards from the bottom of touch-sensitive display unit 1602.

In some embodiments, processing unit 1610 is further configured to:while in a normal power mode, produce (e.g., with an output producingunit 1624) a first output responsive to input at touch-sensitive displayunit 1602, a second output responsive to input at least one hardwarebutton unit 1650, and a third output responsive to input at rotatableinput mechanism unit 1652; and in accordance with the determination thatthe battery level is at or below the first threshold value: enter (e.g.,with a power mode unit 1626) a low-power mode, the low-power modecharacterized in that a fourth output is produced responsive to input atany of touch-sensitive display unit 1602, the at least one hardwarebutton unit 1650, or rotatable input mechanism unit 1652.

In some embodiments, the fourth output is different from the firstoutput, the second output, and the third output.

In some embodiments, the fourth output comprises a display of thecurrent time on touch-sensitive display unit 1602.

In some embodiments, the fourth output comprises a display of anindication of the battery level of battery unit 1606 on touch-sensitivedisplay unit 1602.

In some embodiments, processing unit 1610 is further configured to:while in the normal power mode: receive (e.g., with data receiving unit1616) third data from at least one of accelerometer unit 1654 andgyroscope unit 1656, and in accordance with a determination that thethird data of the at least one of accelerometer unit 1654 and gyroscopeunit 1656 exceeds a predetermined value, produce (e.g., with outputproducing unit 1624) a fifth output.

In some embodiments, processing unit 1610 is further configured to:while in the low-power mode: receive (e.g., with data receiving unit1616) the third data from the at least one of accelerometer unit 1654and gyroscope unit 1656, and in accordance with a determination that thethird data of the at least one of accelerometer unit 1654 and gyroscopeunit 1656 exceeds the predetermined value, produce (e.g., with outputproducing unit 1624) the fourth output.

The operations described above with reference to FIG. 13 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.16. For example, battery level determining operation 1302, haptic outputcausing operation 1304, and data receiving operation 1306 may beimplemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 17 shows an exemplaryfunctional block diagram of an electronic device 1700 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 1700 are configured to perform the techniques described above.The functional blocks of the device 1700 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 17 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 17, an electronic device 1700 includes atouch-sensitive display unit 1702, a battery unit 1706, a hardwarebutton unit 1708, a rotatable input mechanism unit 1710, and aprocessing unit 1712 coupled to touch-sensitive display unit 1702,battery unit 1706, hardware button unit 1708, and rotatable inputmechanism unit 1710. Processing unit 1712 includes a battery leveldetermining unit 1714, a power mode unit 1716, and an output producingunit 1718. Optionally, electronic device 1700 includes a hapticmechanism unit 1752, an accelerometer unit 1754, and a gyroscope unit1756, all of which are coupled to processing unit 1712. Optionally,processing unit 1712 includes a display enabling unit 1720, an inputdetecting unit 1722, a data receiving unit 1724, and a haptic mechanismcontrolling unit 1726.

Processing unit 1712 is configured to: while in a normal power mode,produce (e.g., with output producing unit 1718) a first outputresponsive to input at touch-sensitive display unit 1702, a secondoutput responsive to input at the at least one hardware button unit1708, and a third output responsive to input at rotatable inputmechanism unit 1710; determine (e.g., with battery level determiningunit 1714) a battery level of battery unit 1706; and in accordance witha determination that the battery level is at or below a first thresholdvalue: enter (e.g., with power mode unit 1716) a low-power mode, thelow-power mode characterized in that a fourth output is producedresponsive to input at any of touch-sensitive display unit 1702, the atleast one hardware button unit 1708, or rotatable input mechanism unit1710.

In some embodiments, entering the low-power mode comprises: enablingdisplay (e.g., with display enabling unit 1720) of a confirmationaffordance for entering the low-power mode; detecting (e.g., with inputdetecting unit 1722) a selection of the confirmation affordance; and inresponse to detecting the selection, entering (e.g., with power modeunit 1716) the low-power mode.

In some embodiments, the fourth output is different than the firstoutput, the second output and the third output.

In some embodiments, the fourth output comprises display of the currenttime on touch-sensitive display unit 1702.

In some embodiments, the fourth output comprises display of anindication of the battery level of battery unit 1706 on touch-sensitivedisplay unit 1702.

In some embodiments, electronic device 1700 further comprises at leastone of accelerometer unit 1754 and gyroscope unit 1756. Processing unit1712 is further coupled to the at least one of accelerometer unit 1754and gyroscope unit 1756.

In some embodiments, processing unit 1712 is further configured to:while in the normal power mode: receive (e.g., with data receiving unit1724) first data from the at least one of accelerometer unit 1754 andgyroscope unit 1756; and in accordance with a determination that thefirst data from the at least one of accelerometer unit 1754 andgyroscope unit 1756 exceeds a predetermined value, produce (e.g., withoutput producing unit 1718) a fifth output.

In some embodiments, processing unit 1712 is further configured to:while in the low-power mode: receive second data of the at least one ofaccelerometer unit 1754 and gyroscope unit 1756; in accordance with adetermination that the second data from the at least one of theaccelerometer unit and the gyroscope unit exceeds the predeterminedvalue, produce (e.g., with output producing unit 1718) the fourthoutput.

In some embodiments, electronic device 1700 further comprises hapticmechanism unit 1752. Processing unit 1712 is coupled to haptic mechanismunit 1752, and is further configured to: in accordance with thedetermination that the battery level is at or below the first thresholdvalue, cause (e.g., with haptic mechanism controlling unit 1726) hapticmechanism unit 1752 to issue a haptic output on electronic device 1700.

In some embodiments, processing unit 1712 is further configured to: inaccordance with the determination that the battery level is at or belowthe first threshold value, enable (e.g., with display enabling unit1720) display of an indication that electronic device 1700 is in alow-power mode.

In some embodiments, processing unit 1712 is further configured to: inaccordance with a determination that the battery level is above thefirst threshold value, enable (e.g., with display enabling unit 1720)display of the time in a first color; and in accordance with adetermination that the battery level is at or below the first thresholdvalue, enable (e.g., with display enabling unit 1720) display of thetime in a second color different from the first color.

In some embodiments, the power needed to enable display of the time inthe second color is lower than the power needed to enable display of thetime in the first color.

In some embodiments, enabling display of the time in the second colorinstead of the first color comprises reducing (e.g., with displayenabling unit 1720) a number of pixels of touch-sensitive display unit1702 used to display the time.

The operations described above with reference to FIG. 14 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.17. For example, battery level determining operation 1402 and low-powermode entering operation 1404 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 18 shows an exemplaryfunctional block diagram of an electronic device 1800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 1800 are configured to perform the techniques described above.The functional blocks of the device 1800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 18 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 18, an electronic device 1800 includes atouch-sensitive display unit 1802, a battery unit 1806, at least twoinput mechanisms (e.g. a first mechanism unit 1808 and a secondmechanism unit 1810), and a processing unit 1812 coupled totouch-sensitive display unit 1802, battery unit 1806, and the at leasttwo input mechanisms (e.g. first mechanism unit 1808 and secondmechanism unit 1810). Processing unit 1812 includes a data receivingunit 1814, a time-determining unit 1816, a display enabling unit 1818,an input detecting unit 1820, and a power mode unit 1822. Optionally,electronic device 1800 includes at least one hardware button unit 1850,a rotatable input mechanism unit 1852, an accelerometer unit 1854, and agyroscope unit 1856, all of which are coupled to processing unit 1812.Optionally, rotatable input mechanism unit 1852 comprises a mechanicalbutton unit 1858. Optionally, rotatable input mechanism 1852 comprises acapacitive button unit 1860. Optionally, processing unit 1812 includesan input detecting unit 1824, an output producing unit 1826, a powermode unit 1828, and a data receiving unit 1830.

Processing unit 1812 is configured to: receive (e.g., with datareceiving unit 1814) first data indicative of an activation of firstinput mechanism unit 1808; receive (e.g., with data receiving unit 1814)second data indicative of an activation of second input mechanism unit1810, wherein the second data is received within a predetermined elapsedtime period from receiving the first data; and in response to receivingthe first data and the second data: determine (e.g., with timedetermining unit 1816) an amount of time remaining before a level ofbattery unit 1806 reaches a first threshold value, enable (e.g., withdisplay enabling unit 1818) display of the amount of time remaining,enable (e.g., with display enabling unit 1818) display of an affordancefor invoking a low-power mode, detect (e.g., with input detecting unit1820) a selection of the affordance, and in response to detecting theselection, enter (e.g., with power mode unit 1822) the low-power mode.

In some embodiments, processing unit 1812 is further configured to: inresponse to detecting the selection: enable (e.g., with display enablingunit 1818) display of an indication that electronic device 1800 is inthe low-power mode, and enable (e.g., with display enabling unit 1818)display of a time.

In some embodiments, electronic device 1800 further comprises at leastone hardware button unit 1850 and rotatable input mechanism unit 1852.Electronic device 1800 is configured to, while in a normal power mode,produce a first output responsive to input at touch-sensitive displayunit 1802, a second output responsive to input at the at least onehardware button unit 1850, and a third output responsive to input atrotatable input mechanism unit 1852. Processing unit 1812 is furtherconfigured to: in accordance with the determination that the batterylevel is at or below the first threshold value: enter (e.g., with powermode 1828) a low-power mode, the low-power mode characterized in that afourth output is produced responsive to input at any of touch-sensitivedisplay unit 1802, the at least one hardware button unit 1850, orrotatable input mechanism unit 1852.

In some embodiments, the fourth output is different than the firstoutput, the second output and the third output.

In some embodiments, the fourth output comprises display of the currenttime on touch-sensitive display unit 1802.

In some embodiments, the fourth output comprises display of anindication of the battery level of battery unit 1806 on touch-sensitivedisplay unit 1802.

In some embodiments, electronic device 1800 further comprises at leastone of accelerometer unit 1854 and gyroscope unit 1856.

In some embodiments, processing unit 1812 is further configured to:while in the normal power mode: receive (e.g., with data receiving unit1830) first data from the at least one of accelerometer unit 1854 andgyroscope unit 1856; and in accordance with a determination that thefirst data of the at least one of accelerometer unit 1854 and gyroscopeunit 1856 exceeds a predetermined value, produce (e.g., with outputproducing unit 1826) a fifth output.

In some embodiments, processing unit 1812 is further configured to:while in the low-power mode: receive (e.g., with data receiving unit1830) second data from the at least one of accelerometer unit 1854 andgyroscope unit 1856; and in accordance with a determination that thesecond data from the at least one of accelerometer unit 1854 andgyroscope unit 1856 exceeds the predetermined value, produce (e.g., withoutput producing unit 1826) the fourth output.

In some embodiments, rotatable input mechanism unit 1852 is alsodepressible. Processing unit 1812 is further configured to: while in thelow-power mode, detect (e.g., with input detecting unit 1820) adepression of rotatable input mechanism unit 1852; determine (e.g., withtime determining unit 1816) a duration of the depression of rotatableinput mechanism unit 1852; and in accordance with a determination thatthe duration of the depression exceeds a predetermined threshold, exit(e.g., with power mode 1828) the low-power mode.

In some embodiments, rotatable input mechanism unit 1852 comprisesmechanical button unit 1858, and the depression represents a press onmechanical button unit 1858.

In some embodiments, rotatable input mechanism unit 1852 comprisescapacitive button unit 1860, and the depression represents a touch oncapacitive button 1860.

The operations described above with reference to FIG. 15 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.18. For example, signal receiving operation 1502, time determiningoperation 1506, and detecting operation 1508 may be implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive display112, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. A non-transitory computer-readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by an electronic device with atouch-sensitive display, cause the electronic device to: determine abattery level of a battery of the electronic device; in accordance witha determination that the battery level is at or below a first thresholdvalue, cause a haptic mechanism to issue a haptic output; receive dataindicative of a user input; determine whether the data has been receivedwithin a predetermined time interval after the haptic output; and inaccordance with a determination that the data has been received withinthe predetermined time interval, display a battery alert on thetouch-sensitive display.
 2. The non-transitory computer-readable storagemedium of claim 1, further comprising instructions to cause theelectronic device to determine the battery level while thetouch-sensitive display is inactive.
 3. The non-transitorycomputer-readable storage medium of claim 1, wherein the data indicativeof a user input is a first data and the user input is a first userinput, and wherein the one or more programs further compriseinstructions to cause the electronic device to: after displaying thebattery alert, receive second data indicative of a second user input;determine whether the second data indicative of the second user inputhas been received within a second time interval after displaying thebattery alert; in accordance with a determination that the second datahas been received within the second time interval, remove the displayedbattery alert from the touch-sensitive display; and in accordance with adetermination that the second data has not been received within thesecond time interval: determine an amount of time remaining before thebattery level reaches a second threshold level, and display the amountof time remaining.
 4. The non-transitory computer-readable storagemedium of claim 3, wherein the second user input corresponds to amovement of the electronic device.
 5. The non-transitorycomputer-readable storage medium of claim 1, further comprisinginstructions to cause the electronic device to: while displaying thebattery alert, detect a third user input; and in response to detectingthe third user input: determine an amount of time remaining before thebattery level reaches a second threshold level, and display the amountof time remaining.
 6. The non-transitory computer-readable storagemedium of claim 5, wherein the third user input is a contact on thetouch-sensitive display.
 7. The non-transitory computer-readable storagemedium of claim 1, wherein the one or more programs further compriseinstructions to cause the electronic device to: detect a swipe on thetouch-sensitive display while the battery alert is displayed; and inresponse to detecting the swipe, remove the displayed battery alert fromthe touch-sensitive display.
 8. The non-transitory computer-readablestorage medium of claim 7, wherein the swipe is a substantially downwardswipe.
 9. The non-transitory computer-readable storage medium of claim7, further comprising instructions to cause the electronic device to:remove the displayed battery alert by displaying an animation thatslides the displayed battery alert off-screen in the direction of theswipe.
 10. The non-transitory computer-readable storage medium of claim7, further comprising instructions to cause the electronic device to:remove the displayed battery alert from the touch-sensitive display bycausing a display of the touch-sensitive display to become inactive. 11.The non-transitory computer-readable storage medium of claim 1, furthercomprising instructions to cause the electronic device to: display thebattery alert by displaying an animation that slides the battery alertupwards from the bottom of the touch-sensitive display.
 12. Thenon-transitory computer-readable storage medium of claim 1, wherein theelectronic device further comprises at least one hardware button and arotatable input mechanism, wherein the electronic device is configuredto, while in a normal power mode, produce a first output responsive toinput at the touch-sensitive display, a second output responsive toinput at the at least one hardware button, and a third output responsiveto input at the rotatable input mechanism, and wherein the one or moreprograms further comprise instructions to cause the electronic deviceto: in accordance with the determination that the battery level is at orbelow the first threshold value: enter a low-power mode, the low-powermode characterized in that a fourth output is produced responsive toinput at any of the touch-sensitive display, the at least one hardwarebutton, or the rotatable input mechanism.
 13. The non-transitorycomputer-readable storage medium of claim 12, wherein the fourth outputis different from the first output, the second output, and the thirdoutput.
 14. The non-transitory computer-readable storage medium of claim12, wherein the fourth output comprises a display of the current time onthe touch-sensitive display.
 15. The non-transitory computer-readablestorage medium of claim 12, wherein the fourth output comprises adisplay of an indication of the battery level of the battery on thetouch-sensitive display.
 16. The non-transitory computer-readablestorage medium of claim 12, wherein the electronic device furthercomprises at least one of an accelerometer and a gyroscope, furthercomprising instructions to cause the electronic device to: while in thenormal power mode: receive third data from the at least one of theaccelerometer and the gyroscope, and in accordance with a determinationthat the third data of the at least one of the accelerometer and thegyroscope exceeds a predetermined value, produce a fifth output.
 17. Thenon-transitory computer-readable storage medium of claim 16, furthercomprising instructions to cause the electronic device to: while in thelow-power mode: receive the third data from the at least one of theaccelerometer and the gyroscope, and in accordance with a determinationthat the third data of the at least one of the accelerometer and thegyroscope exceeds the predetermined value, produce the fourth output.18. A method, comprising: at an electronic device with a touch-sensitivedisplay, a battery, and a haptic mechanism: determining a battery levelof the battery; in accordance with a determination that the batterylevel is at or below a first threshold value, causing the hapticmechanism to issue a haptic output; receiving data indicative of a userinput; determining whether the data has been received within apredetermined time interval after the haptic output; and in accordancewith a determination that the data has been received within thepredetermined time interval, displaying a battery alert on thetouch-sensitive display.
 19. An electronic device, comprising: abattery; a haptic mechanism; a touch-sensitive display; a memory; and aprocessor coupled to the battery, the haptic mechanism, thetouch-sensitive display, and the memory, the processor configured to:determine a battery level of the battery; in accordance with adetermination that the battery level is at or below a first thresholdvalue, cause the haptic mechanism to issue a haptic output; receive dataindicative of a user input; determine whether the data has been receivedwithin a predetermined time interval after the haptic output; and inaccordance with a determination that the data has been received withinthe predetermined time interval, display a battery alert on thetouch-sensitive display.